-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactoring/remove the EffectiveConfiguration property in the GitVersionContext class #3215
Refactoring/remove the EffectiveConfiguration property in the GitVersionContext class #3215
Conversation
…ionContext class. This change is a preparation for fixing the issue GitTools#3101 in PR GitTools#3190 and targets the v5 version. No business logic changed.
Hi @asbjornu and @arturcic. Do you have an idea why the CI pipeline not passing? CodeQL / Analyze (csharp) (pull_request):
CI / Unit Test code (windows-latest, net5.0) (pull_request):
|
I will check this one |
@HHobeck seems like recently codeql changed a bit the way they run the build so I had to fix that. You will need to rebase on top of support/5.x to have this fixed |
@arturcic, we also have a problem with the
I think the issue may be that that the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for your hard work on this @HHobeck! It is much appreciated. 🙏🏼 Please have a look at my review comments. As soon as they are resolved and the tests are fixed, I think this should be merged. Then we'll do a merge of support/5.x
into main
so you can rebase #3190 on top of the great work you've done here.
....Core.Tests/Configuration/ConfigProviderTests.CanWriteOutEffectiveConfiguration.approved.txt
Show resolved
Hide resolved
src/GitVersion.Core/VersionCalculation/NextVersionCalculator.cs
Outdated
Show resolved
Hide resolved
src/GitVersion.Core/VersionCalculation/SemanticVersioning/VersionField.cs
Show resolved
Hide resolved
src/GitVersion.Core/Configuration/BranchConfigurationCalculator.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏🏼 Now we just need to figure out what to do with the failing Test Summary
task. Thoughts @arturcic?
The interesting thing is on main the Test summary works just fine, sometimes the macos is failing but on rerun it's ok |
Is it really fine, or does it work when |
if you check this run for example https://github.com/GitTools/GitVersion/actions/runs/3173292935 you will see 5 test summaries for every platform excluding macos + netcore3.1 |
What does this mean? I can see the following error:
On the main branch this error seems to be not existing. |
@HHobeck I think on support branch we can disable the test-summary action, so please rebase again on support branch, I disabled it there |
No problem I can do this. Please let me know if you have changed it. |
@HHobeck you can rebase it now |
…emove-git-version-context-configuration
@HHobeck you don't need to push new commits to re-trigger the failed unit test step. I can retrigger it |
Yes, that is the plan |
Thank you @HHobeck for your contribution! |
🎉 This issue has been resolved in version 5.11.0 🎉 Your GitReleaseManager bot 📦🚀 |
Description
Refactoring/remove the EffectiveConfiguration property in the GitVersionContext class. This change is a preparation for fixing the issue #3101 in PR #3190 and targets the v5 version. No business logic changed.
Related Issue
[Bug] Version not generated correct when creating a feature branch from a release branch #3101
Motivation and Context
This PR is a preparation for PR #3190 and should be integrated in v5.
How Has This Been Tested?
All unit and integration tests have been executed.
Screenshots (if appropriate):
Checklist: